Open
Conversation
…tead of using \n in a TextTag to start a new line
Contributor
|
The new method and function looks good to me. But I have one question. May I ask why we should switch to |
Author
|
When |
|
https://open.feishu.cn/document/ukTMukTMukTM/uMDMxEjLzATMx4yMwETM |
crispgm
force-pushed
the
main
branch
2 times, most recently
from
1af16ed to
7ae6746
Compare
crispgm
force-pushed
the
main
branch
2 times, most recently
from
1e8532a to
c231aca
Compare
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
supports to build multi-line rich text (or say multi-segment rich text in a single post) by using NewLine() method, instead of using
\nin a TextTag to start a new line.See discuss on #42